System for an automated dispensing and retrieval kiosk for recorded media

ABSTRACT

A system for an automated dispensing and retrieval kiosk for recorded media includes a kiosk having a plurality of vertical racks arranged in a circular formation, each vertical rack configured for storing a plurality of recorded media. A customer interface allows a customer to select or return a recorded media. A robotic element delivers the selected recorded media from the vertical racks to a media output, at the customer interface. The element also delivers a returned recorded media from a media input at the customer interface to the vertical racks. A computer controls operation of the kiosk, and an internet interface connects the kiosk to the Internet. The kiosk may communicate with a central server and/or other kiosks of a group, to locate a requested recorded media within a kiosk of the group. Once located within the group, the requested media may be reserved for customer pick-up.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a divisional of U.S. patent application Ser. No.11/366,966, which was filed on Mar. 1, 2006, and which claims thebenefit of priority to and is a continuation-in-part with respect toU.S. Provisional Patent Application No. 60/657,844, which was filed Mar.1, 2005, each of which is incorporated herein by reference to the sameextent as though fully replicated herein.

REFERENCE TO SEQUENCE LISTING

This specification is accompanied by sequence listings provided in theattached Appendices A-N, each of which are incorporated by reference asthough fully replicated herein, and in the CD-ROM submitted herewith, induplicate. The material submitted on CD-ROM also includes source code,submitted as Appendix N and also incorporated by reference as thoughfully replicated herein. Appendix N includes the following electronicfiles:

TABLE A FILENAME DATE SIZE app30_migration.sql Oct. 2, 2003 1053delta_prod_data_migration.sql Oct. 10, 2003 66319 identity_reset.txtOct. 7, 2003 2022 prod_data_migration.sql Oct. 10, 2003 76378steps_data_migration.txt Sep. 29, 2003 501 vl.6newtables.sh Jan. 9, 20041310 v1.6proc.sh Feb. 27, 2004 2871 v1.6table.sql Jan. 26, 2004 41721v1.6trigger.sh Jan. 9, 2004 1381 v1.6view.sh Jan. 9, 2004 2353ffadddelinquent.sql Jun. 18, 2003 915 ffaddfranchisetitletypecap.sqlSep. 5, 2003 798 ffbjpopulatekioskdailysummary.sql Oct. 30, 2003 1333ffbjpopulatereusablepromobydate.sql Nov. 23, 2003 1538ffcheckconfirmrequest.sql Nov. 25, 2003 1358ffcheckfailuretransaction.sql Jul. 31, 2003 699ffcheckinvaidoptionid.sql Jul. 31, 2003 440 ffchecklastheartbeat.sqlFeb. 26, 2004 942 ffconfirmlinestatus.sql Oct. 8, 2003 1082ffcopyfranchise.sql Dec. 4, 2003 14675 ffcopykiosk.sql Dec. 4, 200314460 ffcopykioskgroup.sql Dec. 4, 2003 5137 ffcopykioskinventory.sqlDec. 4, 2003 6687 ffdeleteadmindisc.sql Oct. 8, 2003 1051ffdeletedelinquent.sql Oct. 30, 2003 584 ffdeletefranchise.sql Sep. 5,2003 2079 ffdeletekiosk.sql Oct. 8, 2003 5018 ffdeletekioskgroup.sqlOct. 8, 2003 1588 ffdeletepaymentcard.sql Oct. 8, 2003 901ffdeletepricemodel.sql Oct. 8, 2003 1611 ffdeletepriceoption.sql Oct. 8,2003 1631 ffdeletepromo.sql Nov. 16, 2003 865 ffdeletepromouse.sql Nov.16, 2003 870 ffdeletespecialpricing.sql Oct. 8, 2003 1168ffdeletetitle.sql Oct. 8, 2003 2044 ffgetalertemail.sql Feb. 26, 2004511 ffgetdelinquentlines.sql Nov. 16, 2003 290ffgetdenormtransactions.sql Nov. 29, 2003 3704 ffgetdisc.sql Nov. 16,2003 6987 ffgetdiscallbyid.sql Sep. 23, 2003 2274 ffgetdiscbyid.sql Nov.16, 2003 2262 ffgetfranchise.sql Jul. 30, 2003 746ffgetfranchiseconfigurable.sql Jan. 5, 2004 5711 ffgetfranchiselist.sqlAug. 28, 2003 1014 ffgetfranchisetitletypecap.sql Jul. 24, 2003 766ffgetfranchisetranslation.sql Feb. 26, 2004 2476 ffgetkioskaction.sqlJul. 23, 2003 401 ffgetkioskactionseqnum.sql Jul. 23, 2003 532ffgetkioskbasicstranslation.sql Jul. 23, 2003 1896ffgetkioskinventory.sql Jan. 9, 2004 4799 ffgetkioskstatusdefinition.sqlJul. 31, 2003 512 ffgetkiosktaxrate.sql Jul. 23, 2003 480ffgetkiosktimezone.sql Nov. 6, 2003 631 ffgetkiosktimezonebykioskid.sqlNov. 6, 2003 542 ffgetkiosktimezoneid.sql Oct. 8, 2003 1126ffgetkiosktitle.sql Jul. 16, 2003 1774 ffgetlineitem.sql Nov. 16, 20033076 ffgetlineitembasic.sql Nov. 16, 2003 2516 ffgetlocale.sql Nov. 16,2003 1236 ffgetoverduelines.sql Nov. 16, 2003 306 ffgetpayment.sql Nov.16, 2003 2761 ffgetpaymentcard.sql Nov. 16, 2003 2812ffgetpaymentcardbynumber.sql Nov. 16, 2003 2816 ffgetpaymentcardid.sqlNov. 16, 2003 1346 ffgetpaymentprocessor.sql Nov. 16, 2003 1186ffgetplaylist.sql Jan. 22, 2004 2446 ffgetprocessorid.sql Jul. 21, 2003439 ffgetprocvendor.sql Jul. 21, 2003 433 ffgetpromocode.sql Feb. 26,2004 3410 ffgetpromoid.sql Jun. 19, 2003 779 ffgetreceiptbasic.sql Jun.18, 2003 1101 ffgetserverconfig.sql Jun. 18, 2003 379 ffgettitle.sqlJul. 21, 2003 2242 ffgettitlelist.sql Jan. 20, 2004 8645ffgettransaction.sql Jul. 21, 2003 2941 ffgettransactionactioncount.sqlAug. 6, 2003 959 ffgettransactionbasic.sql Nov. 16, 2003 1392ffgettransactionlinecount.sql Jun. 20, 2003 595ffgettransactionpromoid.sql Sep. 25, 2003 695 ffgettransactiontotals.sqlSep. 29, 2003 2478 ffgettransactiontypeid.sql Nov. 16, 2003 863ffgetunknowndiscbasic.sql Aug. 26, 2003 596 ffisdiscexist.sql Nov. 16,2003 516 ffisinnochargeperiod.sql Jun. 11, 2003 1301ffislineitemexist.sql Jun. 11, 2003 485 ffispaymentcardexist.sql Jun.19, 2003 754 ffispaymentexist.sql Jun. 19, 2003 479ffistransactionexist.sql Jun. 11, 2003 505ffpadddefaultfranchisetitletypecap.sql Oct. 8, 2003 1929 ffpadddisc.sqlOct. 14, 2003 1945 ffpaddfranchisetranslation.sql Oct. 3, 2003 1750ffpaddkioskbasicstranslation.sql Oct. 3, 2003 1680ffpaddpropertygroupandmember.sql Jan. 7, 2004 3514 ffpdeletedisc.sqlOct. 3, 2003 1621 ffpdeletediscbykioskandslot.sql Aug. 21, 2003 1639ffpdeletepropertygroupandmember.sql Jan. 7, 2004 4471ffpgetdefaultlastupdatedby.sql Jun. 11, 2003 441ffpgetpricemodeldependency.sql Sep. 4, 2003 1073ffpgetpriceoptiondependency.sql Sep. 5, 2003 1170ffpopulatelegacytitle.sql Feb. 26, 2004 3080 ffpopulatetitle.sql Feb.26, 2004 3635 ffpsavefranchiseconfigurable.sql Jan. 5, 2004 6384ffpsavepromo.sql Feb. 26, 2004 2912 ffpupdatedisc.sql Aug. 19, 2003 2089ffpupdatefranchisetranslation.sql Sep. 11, 2003 1944ffpupdatekioskbasicstranslation.sql Sep. 4, 2003 1777ffrptkioskactivity.sql Nov. 26, 2003 5802 ffrptkioskdailysummary.sqlOct. 20, 2003 14118 ffrptreusablepromobydate.sql Sep. 24, 2003 10651ffrptuigetvalidpromocodeid.sql Oct. 7, 2003 1465ffrptusedoncepromobydate.sql Sep. 23, 2003 10309 ffsaveadmindisc.sqlOct. 19, 2003 4485 ffsavedefaultkiosk.sql Feb. 26, 2004 3601ffsavedisc.sql Nov. 16, 2003 5153 ffsavedischistory.sql Nov. 16, 20031212 ffsavefranchise.sql Feb. 26, 2004 5581 ffsavekiosk.sql Feb. 26,2004 6614 ffsavekioskgroup.sql Oct. 3, 2003 1846 ffsavekioskslot.sqlOct. 14, 2003 1515 ffsavelineitem.sql Feb. 26, 2004 5292ffsavelocale.sql Nov. 16, 2003 1097 ffsavepayment.sql Nov. 16, 2003 3563ffsavepaymentcard.sql Nov. 16, 2003 4646 ffsaveplayitem.sql Jan. 7, 20041871 ffsaveplaylist.sql Jan. 7, 2004 7827 ffsavepricemodel.sql Feb. 27,2004 3747 ffsavepriceoption.sql Feb. 27, 2004 3792 ffsavepromouse.sqlNov. 16, 2003 2557 ffsavepropertygroup.sql Jan. 7, 2004 1228ffsavepropertygroupmember.sql Jan. 7, 2004 968ffsavepropertyplayitempolicy.sql Jan. 7, 2004 1336ffsaveregularpricing.sql Feb. 27, 2004 2852 ffsavereusablepromo.sql Jul.21, 2003 725 ffsavespecialpricing.sql Feb. 27, 2004 2870 ffsavetitle.sqlFeb. 26, 2004 3910 ffsavetitletranslation.sql Feb. 26, 2004 3204ffsavetransaction.sql Feb. 26, 2004 4630 ffsaveuseoncepercardpromo.sqlJul. 21, 2003 743 ffsaveuseoncepromo.sql Jul. 21, 2003 722ffupdatekioskaction.sql Jul. 23, 2003 622 ffupdatekioskbasics.sql Oct.8, 2003 1547 ffupdatekiosklastalertnonstatus.sql Jan. 6, 2004 1245ffupdatekiosklastalertstatus.sql Jan. 6, 2004 1212 ffupdatekioskping.sqlNov. 16, 2003 1375 ffupdatekiosksetup.sql Oct. 8, 2003 4780ffupdatepromoline.sql Nov. 16, 2003 1125 ffupdatetitledescription.sqlJan. 7, 2004 879 fftdefaultpricing.sql Jun. 23, 2003 706fftdelinquent.sql Jul. 2, 2003 995 fftdischistory.sql Jun. 27, 2003 797fftdiscinventory.sql Jun. 27, 2003 1256 fftdiscstatus.sql Aug. 15, 2003550 fftdwkioskdailysummary.sql Sep. 11, 2003 863ffidwreusablepromobydate.sql Sep. 24, 2003 670fftdwusedoncepromobydate.sql Sep. 11, 2003 588 fftformattranslation.sqlJul. 21, 2003 601 fftfranchise.sql Nov. 16, 2003 1902fftfranchisetitletypecap.sql Jul. 22, 2003 793fftfranchisetranslation.sql Feb. 26, 2004 1288 fftgenre.sql Jul. 2, 2003541 fftgenretranslation.sql Jul. 14, 2003 599 fftgroupcode.sql Nov. 16,2003 542 fftgroupcodekioskgroup.sql Aug. 7, 2003 678 fftkioskaction.sqlJul. 22, 2003 592 fftkioskbaiscstranslation.sql Jul. 21, 2003 1093fftkioskbasics.sql Nov. 16, 2003 1841 fftkioskgroup.sql Nov. 16, 2003579 fftkioskpaymentcardtype.sql Nov. 16, 2003 606 fftkiosksetup.sql Nov.16, 2003 1897 fftkioskslot.sql Sep. 4, 2003 671 fftkioskstatus.sql Feb.26, 2004 1017 fftlineitem.sql Nov. 16, 2003 1623 fftlocale.sql Nov. 16,2003 740 fftlogin.sql Nov. 16, 2003 668 fftloginrole.sql Nov. 16, 2003522 fftlookup.sql Jul. 10, 2003 624 fftlookuptranslation.sql Jul. 21,2003 723 fftlookuptype.sql Jun. 27, 2003 523 fftmedia.sql Jul. 21, 2003679 fftoperation.sql Aug. 27, 2003 542 fftpage.sql Nov. 16, 2003 611fftpayment.sql Nov. 16, 2003 1096 fftpaymentcard.sql Nov. 16, 2003 1270fftpaymentcardtype.sql Nov. 16, 2003 654fftpaymentcardtypetranslation.sql Nov. 16, 2003 696 fftplaylist.sql Nov.16, 2003 964 fftpricemodel.sql Jul. 21, 2003 581 fftpriceoption.sql Jul.21, 2003 595 fftprocessor.sql Jun. 27, 2003 551 fftpromo.sql Feb. 26,2004 928 fftpromotype.sql Jun. 27, 2003 573 fftpromouse.sql Jun. 27,2003 687 fftpropertygroup.sql Jan. 20, 2004 874fftpropertygroupmember.sql Dec. 30, 2003 738 fftpropertyplayitem.sqlDec. 30, 2003 991 fftpropertyplayitempolicy.sql Dec. 30, 2003 791fftrating.sql Jun. 23, 2003 572 fftratingsystem.sql Jun. 23, 2003 578fftregularpricing.sql Nov. 16, 2003 1009 fftresource.sql Jul. 15, 2003633 fftrole.sql Jul. 25, 2003 592 fftrolepagerights.sql Jun. 23, 2003645 fftsequence.sql Jun. 11, 2003 545 fftserverconfig.sql Nov. 16, 2003665 fftsitetype.sql Jun. 23, 2003 519 fftspecialpricing.sql Nov. 16,2003 1053 ffttexttransalation.sql Nov. 16, 2003 692ffttimezonetranslation.sql Jan. 9, 2004 625 ffttitle.sql Nov. 16, 20031176 ffttitletranslation.sql Nov. 16, 2003 1022 ffttitletype.sql Nov.16, 2003 536 ffttitletypetranslation.sql Feb. 26, 2004 661ffttmpident.sql Oct. 5, 2003 522 ffttransaction.sql Nov. 16, 2003 1489tr_fftdefaultpricing_u.sql Sep. 19, 2003 384 tr_fftdelinquent_u.sql Oct.10, 2003 360 tr_fftdischistory_u.sql Nov. 16, 2003 368tr_fftdiscinventory_u.sql Nov. 16, 2003 376 tr_fftdiscstatus_u.sql Aug.15, 2003 361 tr_fftformattranstation_u.sql Oct. 10, 2003 442tr_fftfranchisetitletypecap_u.sql Jul. 22, 2003 530tr_fftfranchisetranslation_u.sql Sep. 19, 2003 462 tr_fftfranchise_u.sqlAug. 7, 2003 354 tr_fftgenretranslation_u.sql Sep. 19, 2003 435tr_fftgenre_u.sql Sep. 19, 2003 326 tr_fftgroupcodekioskgroup_u.sql Aug.7, 2003 466 tr_fftgroupcode_u.sql Aug. 7, 2003 354tr_fftkioskaction_u.sql Jul. 22, 2003 416tr_fftkioskbasicstranslation_u.sql Sep. 4, 2003 464tr_fftkioskbasics_u.sql Jul. 29, 2003 356 tr_fftkioskgroup_u.sql Oct.10, 2003 361 tr_fftkioskpaymentcardtype_u.sql Jul. 25, 2003 473tr_fftkiosksetup_u.sql Oct. 10, 2003 353 tr_fftkioskslot_u.sql Sep. 4,2003 392 tr_fftkioskstatus_u.sql Oct. 10, 2003 356 tr_fftlineitem_u.sqlNov. 16, 2003 347 tr_fftlocale_u.sql Nov. 16, 2003 333tr_fftloginrole_u.sql Jul. 25, 2003 396 tr_fftlogin_u.sql Jul. 25, 2003386 tr_fftlookuptranslation_u.sql Oct. 10, 2003 444tr_fftlookuptype_u.sql Oct. 10, 2003 351 tr_fftlookup_u.sql Oct. 10,2003 335 tr_ffloperation_u.sql Aug. 26, 2003 354 tr_fftpage_u.sql Oct.10, 2003 319 tr_fftpaymentcardtypetranslation_u.sql Jul. 25, 2003 505tr_fftpaymentcardtype_u.sql Jul. 25, 2003 396 tr_fftpaymentcard_u.sqlNov. 16, 2003 368 tr_fftpayment_u.sql Nov. 16, 2003 340tr_fftplaylist_u.sql Aug. 1, 2003 519 tr_fftpricemodel_u.sql Oct. 10,2003 421 tr_fftpriceoption_u.sql Oct. 10, 2003 428 tr_fftprocessor_u.sqlOct. 10, 2003 354 tr_fftpromotype_u.sql Oct. 10, 2003 355tr_fftpromouse_u.sql Oct. 10, 2003 348 tr_fftpromo_u.sql Oct. 10, 2003328 tr_fftpropertygroupmember_u.sql Dec. 30, 2003 528tr_fftpropertygroup_u.sql Dec. 30, 2003 382tr_fftpropertyplayitempolicy_u.sql Dec. 30, 2003 429tr_fftpropertyplayitem_u.sql Dec. 30, 2003 387 tr_fftratingsystem_u.sqlOct. 10, 2003 375 tr_fftrating_u.sql Oct. 10, 2003 333tr_fftregularpricing_u.sql Aug. 27, 2003 389 tr_fftrolepagerights_u.sqlOct. 10, 2003 459 tr_fftrole_u.sql Jul. 25, 2003 319tr_fftserverconfig_u.sql Jul. 31, 2003 375 tr_fftsitetype_u.sql Oct. 10,2003 347 tr_fftspecialpricing_u.sql Aug. 27, 2003 389tr_ffttexttranslation_u.sql Jul. 22, 2003 468tr_ffttimezonetranslation_u.sql Jan. 9, 2004 456tr_ffttitletranslation_u.sql Aug. 26, 2003 435tr_ffttitletypetranslation_u.sql Jul. 25, 2003 463 tr_ffttitletype_u.sqlJul. 25, 2003 354 tr_ffttitle_u.sql Aug. 26, 2003 326tr_ffttransaction_u.sql Nov. 16, 2003 368 ffdefaultpricing.sql Jun. 23,2003 586 ffdelinquent.sql Jun. 18, 2003 672 ffdiscdetail.sql Jul. 4,2003 426 ffdischistory.sql Jun. 27, 2003 596 ffdiscinventory.sql Nov.16, 2003 1358 ffdiscinventoryall.sql Sep. 23, 2003 1341 ffdiscstatus.sqlAug. 15, 2003 420 ffdwkioskdailysummary.sql Sep. 11, 2003 756ffdwreusablepromobydate.sql Sep. 11, 2003 539ffdwusedoncepromobydate.sql Sep. 11, 2003 472 ffformattranslation.sqlJul. 15, 2003 470 fffranchise.sql Nov. 16, 2003 900fffranchiseandprocessor.sql Oct. 19, 2003 1205fffranchiseandtranslation.sql Feb. 26, 2004 1843fffranchisetitletypecap.sql Aug. 29, 2003 655 fffranchisetranslation.sqlFeb. 26, 2004 1050 ffgenre.sql Nov. 16, 2003 442ffgenreandtranslation.sql Nov. 16, 2003 710 ffgenretranslation.sql Nov.16, 2003 480 ffgraphicplaylist.sql Jan. 27, 2004 4078 ffgroupcode.sqlNov. 16, 2003 433 ffgroupcodekioskgroup.sql Aug. 29, 2003 514ffkiosk.sql Nov. 16, 2003 1130 ffkioskaction.sql Aug. 29, 2003 505ffkioskbadslot.sql Sep. 4, 2003 281 ffkioskbasics.sql Nov. 16, 2003 1679ffkioskbasicsandsetup.sql Nov. 16, 2003 1734ffkioskbasicsandtranslation.sql Nov. 16, 2003 2460ffkioskbasicstranslation.sql Nov. 16, 2003 952 ffkioskgenre.sql Nov. 16,2003 636 ffkioskgroup.sql Nov. 16, 2003 476 ffkioskgroupcode.sql Nov.16, 2003 764 ffkiosklocale.sql Nov. 16, 2003 575 ffkioskpaymentcard.sqlNov. 16, 2003 2203 ffkioskpaymentcardtype.sql Nov. 16, 2003 515ffkioskproperty.sql Jan. 8, 2004 936 ffkioskrating.sql Nov. 16, 2003 642ffkioskratingsystem.sql Nov. 16, 2003 634 ffkioskregularpricing.sql Feb.26, 2004 750 ffkioskrolelogin.sql Aug. 29, 2003 1254 ffkioskrolepage.sqlSep. 29, 2003 499 ffkiosksetup.sql Nov. 16, 2003 2090 ffkioskslot.sqlSep. 4, 2003 459 ffkioskslotoffset.sql Sep. 4, 2003 291ffkioskspecialpricing.sql Feb. 26, 2004 791 ffkioskstatus.sql Feb. 26,2004 949 ffkiosktexttranslation.sql Nov. 16, 2003 1186 ffkiosktitle.sqlNov. 16, 2003 1444 ffkiosktitletype.sql Feb. 26, 2004 1725ffkiosktitletypecap.sql Feb. 26, 2004 1782 fflineitem.sql Nov. 16, 20031892 fflocale.sql Nov. 16, 2003 615 fflogin.sql Nov. 16, 2003 538ffloginrole.sql Nov. 16, 2003 420 fflookup.sql Jul. 15, 2003 564fflookupandtranslation.sql Nov. 16, 2003 1261 fflookuptranslation.sqlNov. 16, 2003 608 fflookuptype.sql Nov. 16, 2003 429 ffmedia.sql Nov.16, 2003 556 ffmediaplaylist.sql Nov. 16, 2003 668 ffoperation.sql Aug.29, 2003 433 ffpage.sql Nov. 16, 2003 480 ffpayment.sql Nov. 16, 20031296 ffpaymentcard.sql Nov. 16, 2003 1181 ffpaymentcardtype.sql Nov. 16,2003 494 ffpaymentcardtypeandtranslation.sql Nov. 16, 2003 861ffpaymentcardtypetranslation.sql Nov. 16, 2003 575 ffpricemodel.sql Nov.16, 2003 478 ffpriceoption.sql Nov. 16, 2003 485 ffprocessor.sql Nov.16, 2003 457 ffpromo.sql Nov. 16, 2003 718 ffpromoall.sql Sep. 23, 2003702 ffpromotype.sql Nov. 16, 2003 433 ffpromouse.sql Nov. 16, 2003 619ffpropertygroup.sql Dec. 30, 2003 611 ffpropertygroupmember.sql Dec. 30,2003 522 ffpropertyplayitem.sql Dec. 30, 2003 661ffpropertyplayitempolicy.sql Dec. 30, 2003 627 ffrating.sql Nov. 16,2003 492 ffratingsystem.sql Nov. 16, 2003 493 ffregularpricing.sql Nov.16, 2003 789 ffresource.sql Nov. 16, 2003 538 ffrole.sql Aug. 29, 2003490 ffrolepagerights.sql Nov. 16, 2003 554 ffsequence.sql Jun. 11, 2003487 ffserverconfig.sql Nov. 16, 2003 510 ffsitetype.sql Nov. 16, 2003426 ffspecialpricing.sql Nov. 16, 2003 805 ffstaticplaylist.sql Nov. 16,2003 587 fftexttranslation.sql Nov. 16, 2003 538fftimezonetranslation.sql Jan. 11, 2004 506 fftitle.sql Nov. 16, 2003991 fftitleandtranslation.sql Nov. 16, 2003 1465 fftitletranslation.sqlNov. 16, 2003 660 fftitletype.sql Nov. 16, 2003 431fftitletypeandtranslation.sql Feb. 26, 2004 783fftitletypetranslation.sql Feb. 26, 2004 553 fftransaction.sql Jul. 21,2003 1164 ffuser.sql Jul. 15, 2003 626 ffvideoplaylist.sql Jan. 27, 20044730 adjustment.sql Jan. 22, 2004 410 aem.sql Jan. 22, 2004 1108discinventory.sql Jan. 22, 2004 776 lineitem.sql Jan. 22, 2004 794promo.sql Jan. 22, 2004 1904 title.sql Feb. 27, 2004 5011transaction.sql Jan. 22, 2004 4195 userpaymentcard.sql Jan. 22, 2004 639aemcomm.txt May 22, 2003 1441 formmail.pl May 19, 2003 29889admin.web.xml Feb. 26, 2004 15414 aemserver.properties Aug. 19, 2003 553aemserver.web.xml Nov. 4, 2003 531 ffserver.properties Feb. 26, 20041802 log.properties Jul. 23, 2003 43 web.xml Nov. 16, 2003 13129datepicker.js Feb. 26, 2004 16723 dateutility.js Oct. 7, 2003 3794navigation.js Jun. 15, 2003 530 simple.css Sep. 26, 2003 2238 utility.jsFeb. 26, 2004 2388 admin.jsp Nov. 16, 2003 3411 companygroupdetails.jspFeb. 26, 2004 24135 companygrouplist.jsp Feb. 26, 2004 9086companygroupquery.jsp Feb. 26, 2004 6226 customerdetails.jsp Feb. 26,2004 10945 customerhistory.jsp Nov. 16, 2003 9781 customerlist.jsp Feb.26, 2004 9766 customerquery.jsp Feb. 26, 2004 4986 dataexport.jsp Feb.26, 2004 13133 discdetails.jsp Feb. 26, 2004 13141 disclist.jsp Feb. 26,2004 13971 discquery.jsp Feb. 26, 2004 4954 dumprequest.jsp Jun. 19,2003 1038 dvdplayerror.jsp Nov. 16, 2003 1452 formatlookup.jsp Nov. 16,2003 7975 formatnamelookup.jsp Nov. 16, 2003 9596 genrelookup.jsp Nov.16, 2003 8890 genrenamelookup.jsp Nov. 16, 2003 9617 helplist.jsp Nov.16, 2003 6460 kioskdetails.jsp Feb. 26, 2004 25905 kiosklist.jsp Feb.26, 2004 10433 kioskquery.jsp Feb. 26, 2004 6167kioskreporterrorpage.jsp Jun. 15, 2003 447 kioskstatus.jsp Nov. 16, 20037546 languagelookup.jsp Nov. 16, 2003 8473 latefeenotify.jsp Feb. 26,2004 5916 login.jsp Nov. 16, 2003 1570 lookuptablesmenu.jsp Nov. 16,2003 5503 marketing.jsp Dec. 31, 2003 4272marketingcommercialdeployment.jsp Jan. 23, 2004 1799marketingcorporatetools.jsp Jan. 23, 2004 3642marketingfranchisereporting.jsp Jan. 23, 2004 1767 menuheader.jsp Feb.26, 2004 3539 pricemodellookup.jsp Feb. 26, 2004 9321priceoptionlookup.jsp Feb. 26, 2004 8828 pricing.jsp Nov. 16, 2003 26132promodetails.jsp Feb. 26, 2004 12625 promolist.jsp Feb. 26, 2004 8487promonotify.jsp Feb. 26, 2004 2569 querypage.jsp Nov. 16, 2003 8023ratinglookup.jsp Nov. 16, 2003 10956 ratingsystemlookup.jsp Nov. 16,2003 9333 refundreceipt.jsp Feb. 26, 2004 5876 rentalreceipt.jsp Feb.26, 2004 7311 reports.jsp Feb. 26, 2004 11091 reportsquery.jsp Feb. 26,2004 26836 reportsreusablecode.jsp Nov. 16, 2003 9134showdvdplayexception.jsp Jun. 19, 2003 176 sitetypelookup.jsp Nov. 16,2003 8381 titledetails.jsp Feb. 26, 2004 41079 titlelist.jsp Feb. 26,2004 11416 titlequery.jsp Feb. 26, 2004 7521 titletypelookup.jsp Nov.16, 2003 8259 titletypenamelookup.jsp Nov. 16, 2003 9782 trailers.jspJan. 23, 2004 8410 transactiondetails.jsp Feb. 26, 2004 38104transactionlist.jsp Feb. 26, 2004 14931 transactionquery.jsp Feb. 26,2004 4630 viewlogfile.jsp Jun. 15, 2003 881 adminenvironment.java Nov.16, 2003 10478 adminserversession.java Oct. 3, 2003 1372adminservlet.java Feb. 26, 2004 20648 cmdgetconstants.java Feb. 26, 20041640 cmdgethelp.java Nov. 16, 2003 1046 cmdgetinit.java Feb. 26, 200448624 cmdgetlookuptables.java Feb. 26, 2004 4318 cmdgetreports.java Nov.16, 2003 1900 command.java Nov. 16, 2003 356 commandexception.java Jun.15, 2003 341 commandtoken.java Nov. 16, 2003 2381ffserverproperties.java Nov. 16, 2003 3418 aem.java Apr. 17, 2004 110537aemapp.java Feb. 26, 2004 13310 aemexception.java Jun. 4, 2003 362aemfactory.java Mar. 1, 2004 375 arm.java Mar. 25, 2004 4836armexception.java Jun. 4, 2003 303 barcode.java Jun. 4, 2003 330barcodereader.java Nov. 16, 2003 1467 bootstrap.java Mar. 10, 2004 1427carousel.java Mar. 25, 2004 10104 carouselexception.java Jun. 4, 2003311 cmdgetkioskdetails.java Feb. 26, 2004 24743 cmdgetkiosklist.javaFeb. 26, 2004 21084 cmdgetkioskstatus.java Nov. 16, 2003 6812creditcard.java Aug. 29, 2003 391 creditcardreader.java Nov. 16, 2003467 creditcardthread.java Nov. 16, 2003 3397 door.java Mar. 25, 20045958 doorexception.java Jun. 4, 2003 304 dpec.java Apr. 6, 2004 12744light.java Mar. 10, 2004 1031 lightexception.java Jun. 4, 2003 304nmc.java Nov. 16, 2003 3431 roller.java Mar. 4, 2004 1360rollerexception.java Jun. 4, 2003 307 sensor.java Mar. 4, 2004 650servo.java Apr. 17, 2004 6865 servocallback.java Apr. 6, 2004 10638servocallbackfactory.java Mar. 10, 2004 799 servoex.java Apr. 17, 200441228 servoexception.java Jun. 5, 2003 304 servofactory.java Apr. 1,2004 2627 servoplus.java Apr. 19, 2004 9392 servoprime.java Feb. 23,2004 199 comm.java Feb. 26, 2004 14481 commexception.java Jun. 17, 2003359 aemgui.java Mar. 30, 2004 17844 commandmap.java Mar. 24, 2004 20760tools.java Mar. 30, 2004 10031 aemserver.java Nov. 16, 2003 9960aemserverconfig.java Nov. 16, 2003 2212 checkpromocodecommand.java Feb.26, 2004 7626 command.java Nov. 16, 2003 730 commandfactory.java Nov.16, 2003 3982 confirmdispense.java Feb. 27, 2004 12432 discremoved.javaNov. 16, 2003 10112 discreturned.java Nov. 16, 2003 10720garbagecollect.java Sep. 10, 2003 2560 getreceipt.java Feb. 26, 20046094 monitorserver.java Sep. 10, 2003 2364 ping.java Nov. 16, 2003 13243processpayment.java Feb. 26, 2004 11065 servletutils.java Feb. 26, 20046180 abstractbottombar.java Jun. 4, 2003 1474 abstractcontentbar.javaFeb. 26, 2004 8080 abstracthardwarethread.java Mar. 1, 2004 1797abstracttoolspanel.java Mar. 3, 2004 21520 abstracttopbar.java Jun. 4,2003 1328 baseactionlistener.java Jan. 21, 2004 1266cmdgetlanguagelookup.java Nov. 16, 2003 17175 dvdplaybase.java Apr. 1,2004 84945 dvdplaylocale.java Oct. 28, 2003 3642 datapacket.dtd May 23,2003 282 datapacketcomposer.java Feb. 26, 2004 23560 nvpair.java May 23,2003 2641 nvpairset.java May 23, 2003 2413 rcset.java Jun. 13, 2003 4183rdatasetfieldvalues.java May 23, 2003 1631 rmetafield.java May 23, 20032608 rmetarow.java May 23, 2003 2736 admindatamodule.java Feb. 26, 200477453 admindatamoduleconstants.java Feb. 26, 2004 63002 column.java Jul.7, 2003 3371 databaseexception.java Jun. 15, 2003 336 databaseutil.javaJun. 15, 2003 2349 dataprovider.java Nov. 16, 2003 885dataproviderfactory.java Nov. 16, 2003 3952 dataproviderpool.java Nov.16, 2003 5781 datarow.java Jul. 7, 2003 4083 datastorage.java Feb. 26,2004 4309 ffserver.properties Jul. 7, 2003 1384 idataprovider.java Jun.4, 2003 780 idataproviderfactory.java Jun. 4, 2003 754 iprocedure.javaFeb. 26, 2004 2480 iquery.java Nov. 16, 2003 9317 locate.java Jul. 7,2003 321 logindatamodule.java Feb. 26, 2004 15240 parameterrow.java Jul.7, 2003 1834 proceduredataset.java Jul. 7, 2003 1222 querydataset.javaFeb. 26, 2004 11611 sqlstates.java Jul. 15, 2003 338 variant.java Jul.7, 2003 11119 variantformatter.java Jul. 7, 2003 961mssqldataprovider.java Nov. 16, 2003 6400 mssqlprocedure.java Feb. 26,2004 64208 mssqlproviderfactory.java Nov. 16, 2003 1580 mssqlquery.javaNov. 16, 2003 48502 ibusinesstransaction.java Jun. 17, 2003 656domdata.java Mar. 19, 2004 70532 domdataexception.java Aug. 7, 2003 363persistencedata.java Feb. 26, 2004 11344 aemserverobjectexception.javaJun. 4, 2003 718 dataaccessexception.java Jun. 4, 2003 1206dvdexception.java Jun. 15, 2003 260 dvdplayexception.java Jul. 2, 20031697 exceptioncodes.java Feb. 26, 2004 4327 authorizingpaymentcard.javaFeb. 26, 2004 4798 badslots.java Nov. 16, 2003 2799 barcampegtest.javaMar. 4, 2004 4855 cardreaderhid.java Nov. 16, 2003 3626 controller.javaFeb. 27, 2004 524 controllerex.java Mar. 4, 2004 19133controllerplus.java Mar. 1, 2004 254 cycletest.java Apr. 9, 2004 14916deliveringdvd.java Nov. 16, 2003 2299 detectingdiscin.java Mar. 10, 20041091 errorlog.java Jun. 6, 2003 505 helpmain.java Feb. 26, 2004 2251identifyingdisc.java Nov. 16, 2003 1362 initializingaem.java Mar. 4,2004 1197 inventorycheck.java Apr. 9, 2004 15969 login.java Mar. 1, 20041764 main.java Apr. 1, 2004 1689 operator.java Mar. 30, 2004 4441pushingdiscalltheway.java Mar. 19, 2004 1938 removediscs.java Mar. 30,2004 7925 removedvd.java Apr. 1, 2004 2597 returnerror.java Mar. 24,2004 1930 returningmovie.java Mar. 19, 2004 1710 servoparams.java Mar.3, 2004 274 servoparamsex.java Mar. 4, 2004 10979 simpleremovediscs.javaMar. 4, 2004 6629 slotcal.java Mar. 3, 2004 270 slotcalex.java Mar. 4,2004 27924 swipepaymentcard.java Nov. 16, 2003 2478unabletorecognizemovie.java Mar. 24, 2004 1727 cmdgetdiscdetails.javaFeb. 26, 2004 10017 cmdgetdisclist.java Feb. 26, 2004 16122cmdgetformatlookup.java Nov. 16, 2003 15415 cmdgetformatnamelookup.javaNov. 16, 2003 8722 cmdgetgenrelookup.java Nov. 16, 2003 15544cmdgetgenrenamelookup.java Nov. 16, 2003 8520 cmdgetratinglookup.javaNov. 16, 2003 18066 cmdgetratingsystemlookup.java Nov. 16, 2003 15652cmdgettitledetails.java Feb. 26, 2004 14730 cmdgettitlelist.java Feb.26, 2004 21641 cmdgettitletypelookup.java Nov. 16, 2003 15598cmdgettitletypenamelookup.java Nov. 16, 2003 8857cmdtrailerplaylist.java Jan. 7, 2004 4945 disc.java Nov. 16, 2003 8892discapp.java Feb. 26, 2004 35064 discindex.java Feb. 26, 2004 4335discindexitem.java Feb. 26, 2004 10380 genreitem.java Jun. 4, 2003 1262inventory.java Mar. 4, 2004 94014 inventoryexception.java Jul. 2, 2003941 localeindex.java Jul. 14, 2003 1177 localeindexitem.java Jul. 14,2003 1135 paymentcardtypeindex.java Aug. 5, 2003 1632paymentcardtypeindexitem.java Aug. 5, 2003 2081 playlist.java Nov. 16,2003 1153 playlistitem.java Feb. 26, 2004 3968 pricingitem.java Feb. 26,2004 5993 slotindex.java Mar. 4, 2004 3519 sorttitlediscindex.java Sep.29, 2003 3648 sorttitlediscindexitem.java Jul. 14, 2003 3182streetdatediscindex.java Sep. 29, 2003 3672 streetdatediscindexitem.javaJul. 14, 2003 3401 title.java Feb. 26, 2004 13961 titleindex.java Nov.16, 2003 2394 titleindexitem.java Jun. 4, 2003 663 titletypeindex.javaJul. 14, 2003 1464 titletypeindexitem.java Feb. 26, 2004 2158dvdplayformatter.java Oct. 10, 2003 2476 dvdplaylevel.java Jul. 29, 2003619 lckfilefilter.java Aug. 1, 2003 557 log.java Feb. 26, 2004 20142logfile.java Nov. 16, 2003 3069 playlistmanager.java Feb. 26, 2004 9086trigger.java Feb. 26, 2004 634 accountmanagertablemode.java Jun. 20,2003 2976 aemcontent.java Feb. 26, 2004 8940 badslotstablemodel.javaNov. 16, 2003 3257 barcodehash.java Jul. 30, 2003 453buttonstatushash.java Jul. 30, 2003 421 discinventorytablemodel.javaNov. 16, 2003 3571 error.java Aug. 6, 2003 2131 help.java Feb. 26, 20043840 popupyesno.java Jul. 30, 2003 383 slotcaltablemodel.java Mar. 3,2004 2894 sortingcolumnmodel.java Nov. 16, 2003 9953 tablemap.java Aug.6, 2003 2078 testconnectionhash.java Jul. 30, 2003 251cmdgetcompanygroupdetails.java Feb. 26, 2004 16756cmdgetcompanygrouplist.java Feb. 26, 2004 16718 cmdgetmarketing.javaDec. 31, 2003 950 cmdgetsitetypelookup.java Nov. 16, 2003 16183franchise.java Feb. 26, 2004 17918 cmdgettransactiondetails.java Feb.26, 2004 17436 cmdgettransactionlist.java Feb. 26, 2004 19933creditcard.java Nov. 16, 2003 7889 emailuser.java Jun. 15, 2003 4995itransaction.java Feb. 26, 2004 565 lineitem.java Feb. 26, 2004 54831payment.java Nov. 16, 2003 33845 paymentcard.java Feb. 26, 2004 30972paymentcardfactory.java Nov. 16, 2003 11065 paymentexception.java Jun.30, 2003 929 paymentprocessor.java Nov. 16, 2003 4331processorfactory.java Nov. 16, 2003 1126 receipt.java Feb. 26, 2004 9970receiptdata.java Jun. 15, 2003 1027 receiptfactory.java Feb. 26, 200417784 receiptlineitem.java Jun. 15, 2003 795 receiptrules.java Feb. 26,2004 13135 refundtransaction.java Feb. 26, 2004 11340regulartransaction.java Feb. 26, 2004 18307 renewaltransaction.java Feb.26, 2004 28121 transaction.java Feb. 26, 2004 24278transactiondetailsbean.java Jun. 15, 2003 343 transactionfactory.javaNov. 16, 2003 2671 verisignexception.java Jul. 2, 2003 932verisignprocessor.java Nov. 16, 2003 11697 verisignrules.java Jun. 15,2003 5507 verisigntransactionbean.java Jun. 15, 2003 3867cmdgetpricemodellookup.java Feb. 26, 2004 16159cmdgetpriceoptionlookup.java Feb. 26, 2004 17304 cmdgetpricing.java Feb.26, 2004 43074 regularpricing.java Sep. 8, 2003 2305 specialpricing.javaSep. 8, 2003 2552 cmdgetpromolist.java Feb. 26, 2004 14242factorypromo.java Feb. 26, 2004 25522 factorypromoreusable.java Feb. 26,2004 3872 factoryuseoncepercardpromo.java Feb. 26, 2004 4065factoryuseoncepromo.java Feb. 26, 2004 4866 ipromo.java Feb. 26, 20042066 ipromolookuptypes.java Sep. 24, 2003 1511 promo.java Feb. 26, 200415338 promocode.java Jun. 15, 2003 3230 promocodelist.java Jun. 15, 2003262 promocollection.java Feb. 26, 2004 1119 promoexception.java Jul. 7,2003 1250 promohistory.java Jul. 7, 2003 2129 promoreusable.java Aug. 4,2003 3911 promostatuses.java Jun. 15, 2003 356 promostorage.java Nov.16, 2003 1474 promotypes.java Jun. 15, 2003 341 promousagecount.javaJul. 7, 2003 592 promouse.java Jun. 15, 2003 1385 promouseonce.java Feb.26, 2004 6383 promouseoncepercard.java Aug. 4, 2003 5013asynchrequest.java May 30, 2003 2620 datarecordrequest.java May 30, 20032149 datasetrequest.java May 30, 2003 5800 getfragmentrequest.java May30, 2003 4622 getpkrecordrequest.java May 30, 2003 4738getrecordrequest.java May 30, 2003 2275 irequest.java Jul. 2, 2003 922pingrequest.java Nov. 16, 2003 3534 queryrequest.java May 30, 2003 2287request.java Nov. 16, 2003 8625 requestfactory.java Nov. 16, 2003 4383requestlogger.java Oct. 8, 2003 1992 synchrequest.java May 30, 2003 2623fragments.java Nov. 16, 2003 2519 requestcontext.java Jun. 27, 2003 1266requestcontroller.java Feb. 26, 2004 18096 aboutcompanyscreen.java Feb.26, 2004 6274 accountmanagerpanel.java Nov. 16, 2003 9183aemstartuperrorscreen.java Feb. 26, 2004 3218applicationinitializing.java Oct. 15, 2003 1471authorizingpaymentscreen.java Feb. 26, 2004 5290 badslotspanel.java Nov.16, 2003 4288 barcampegtestpanel.java Feb. 27, 2004 8513cardreaderhidpanel.java Nov. 16, 2003 3210 carttablescreen.java Feb. 26,2004 18426 controllerpanel.java Feb. 27, 2004 270 controllerpanelex.javaFeb. 23, 2004 26290 controllerpanelfactory.java Mar. 29, 2004 921controllerpanelplus.java Mar. 1, 2004 268 cycletestpanel.java Nov. 16,2003 5178 deliveringdvdscreen.java Feb. 26, 2004 8591discnotbelongscreen.java Feb. 26, 2004 4144 dvddescriptionscreen.javaFeb. 26, 2004 29758 emailscreen.java Feb. 26, 2004 8103errorlogpanel.java Nov. 16, 2003 1102 errorscreen.java Feb. 26, 200413401 gamedescriptionscreen.java Feb. 26, 2004 24581gameselectionscreen.java Nov. 16, 2003 27734 helpanswerscreen.java Feb.26, 2004 16534 helpmainscreen.java Feb. 26, 2004 11272identifyingmoviescreen.java Feb. 26, 2004 5071initializingaemscreen.java Feb. 26, 2004 3766 inventorycheckpanel.javaNov. 16, 2003 2251 loginpanel.java Feb. 26, 2004 5249 mainscreen.javaMar. 30, 2004 15635 maximumdiscexceededscreen.java Jan. 22, 2004 16350movieselectionscreen.java Feb. 26, 2004 28745 mustbe18screen.java Feb.26, 2004 7475 operatorpanel.java Nov. 16, 2003 7544outoforderscreen.java Dec. 30, 2003 7255 paymentcardapprovedscreen.javaFeb. 26, 2004 8836 promocodedescriptionscreen.java Feb. 26, 2004 6761promocodescreen.java Feb. 26, 2004 12698 pushingdiscallthewayscreen.javaFeb. 26, 2004 4632 removediscspanel.java Nov. 16, 2003 6089removedvdscreen.java Feb. 26, 2004 5700 rentalagreementscreen.java Feb.26, 2004 15895 returnerrorscreen.java Feb. 26, 2004 4932returningmoviescreen.java Feb. 26, 2004 4971 returnmoviescreen.java Feb.26, 2004 5845 returnthankyouscreen.java Apr. 7, 2004 15583servoparamspanel.java Mar. 1, 2004 268 servoparamspanelex.java Mar. 1,2004 14613 servoparamspanelfactory.java Mar. 29, 2004 926servoparamspanelplus.java Mar. 1, 2004 223 simpleremovediscspanel.javaFeb. 26, 2004 6620 slotcalpanel.java Mar. 1, 2004 264slotcalpanelex.java Mar. 3, 2004 10092 slotcalpanelfactory.java Mar. 29,2004 902 slotcalpanelplus.java Mar. 1, 2004 265swipepaymentcardscreen.java Feb. 26, 2004 11557 timeoutscreen.java Feb.26, 2004 9421 unabletorecognizemoviescreen.java Feb. 26, 2004 9386zipcodescreen.java Feb. 26, 2004 8510 email.java Feb. 26, 2004 8478heartbeatmonitor.java Feb. 26, 2004 24765 heartbeatthread.java Apr. 6,2004 3675 iemail.java Feb. 26, 2004 915 ievent.java Jun. 25, 2003 265missingpostersthread.java Nov. 16, 2003 7848 missingtrailersthread.javaFeb. 26, 2004 11914 queue.java Feb. 26, 2004 8012 queueexception.javaJun. 4, 2003 357 queuejob.java Feb. 26, 2004 5743 queuethread.java Nov.16, 2003 572 sendlogthread.java Aug. 19, 2003 1400servercommandthread.java Apr. 6, 2004 8271 shutdownthread.java Nov. 16,2003 1276 taskexception.java Aug. 18, 2003 911 dbaddtitles.java Oct. 10,2003 8535 dbconnection.java Feb. 26, 2004 1433 dbinterbasemigration.javaOct. 6, 2003 6613 dblegacytitles.java Oct. 10, 2003 6745dbmediaplaylist.java Oct. 31, 2003 5890 dbservercommand.java Oct. 31,2003 3927 dbstaticplaylist.java Oct. 31, 2003 5079dbunicodeaddtitles.java Nov. 16, 2003 16407 dbupdate.java Jun. 27, 20035252 dbupdatemfg.java Sep. 12, 2003 15148 garbagecollect.java Nov. 16,2003 2238 monitorserver.java Feb. 26, 2004 4035 monitorserverthread.javaNov. 21, 2003 4870 sendaemdata.java Sep. 4, 2003 3558sendpersistencedata.java Sep. 4, 2003 2399 updatechecksum.java Sep. 4,2003 3088 screenproperties.java Feb. 26, 2004 12070 texttorows.java Nov.16, 2003 1818 cmdgetcustomerdetails.java Feb. 26, 2004 3596cmdgetcustomerhistory.java Nov. 16, 2003 11932 cmdgetcustomerlist.javaFeb. 26, 2004 11182 customerdetailsbean.java Jun. 15, 2003 337 user.javaJun. 15, 2003 5411 useractions.java Nov. 16, 2003 5003 userstorage.javaNov. 16, 2003 5957 discaction.java Mar. 4, 2004 3510discactionexception.java Jun. 4, 2003 378 discfound.java Nov. 16, 20036380 discitem.java Jun. 4, 2003 528 discmissing.java Nov. 16, 2003 4576discremove.java Nov. 16, 2003 5859 discrental.java Nov. 16, 2003 17957discrentalexception.java Jun. 4, 2003 378 discreturn.java Nov. 16, 20039215 groupcodeexception.java Jul. 14, 2003 326maxdiscsallowedexception.java Jun. 25, 2003 436nodiscinslotexception.java Aug. 5, 2003 377processpaymentvalidationexception.java Aug. 5, 2003 398promocodeexception.java Aug. 5, 2003 368 removeop.java Apr. 9, 2004 3512removeopexception.java Jun. 4, 2003 374 rentop.java Apr. 9, 2004 16824rentopexception.java Jul. 2, 2003 461 returnop.java Mar. 25, 2004 7030returnopexception.java Jun. 4, 2003 375 environment.java Nov. 16, 20034885 execcommandline.java Feb. 26, 2004 3979 formatutil.java Jun. 15,2003 8269 formatutility.java Jun. 15, 2003 2542 ienvironment.java Sep.10, 2003 668 lookuptable.java Jun. 15, 2003 566 reportutil.java Feb. 26,2004 2732 stopwatch.java Aug. 6, 2003 935 util.java Feb. 26, 2004 21009utility.java Jun. 15, 2003 19615 bottombarmode.java Feb. 26, 2004 16129curvedborder.java Jun. 4, 2003 1148 keyboardassembler.java Feb. 26, 20046959 tablerenderer.java Jun. 4, 2003 812 topbannodel.java Feb. 26, 20046515 utility.java Nov. 16, 2003 2243 addtitles.bat Nov. 3, 2003 562aemapp.bat Oct. 16, 2003 553 aemboot.bat Oct. 13, 2003 313 aemclosed.batJan. 27, 2004 152 aemcreate.bat Oct. 8, 2003 549 aemdisplayoff.bat Apr.19, 2004 61 aemdisplayon.bat Apr. 19, 2004 60 aeminst.bat Aug. 7, 2003366 aemmigrate.bat Oct. 8, 2003 541 aemship.bat Oct. 13, 2003 413aemstandalone.bat Oct. 8, 2003 419 aemstartapp.bat Oct. 16, 2003 400aemstartapp.vbs Mar. 5, 2004 1601 aemtools.bat Oct. 8, 2003 4680overdue.txt Feb. 5, 2004 155 0promonotify.txt Feb. 5, 2004 1080refund.txt Feb. 5, 2004 99 0rental.txt Feb. 5, 2004 108alert.content.txt Feb. 26, 2004 143

TECHNICAL FIELD

This invention relates to a system for an automated dispensing andretrieval kiosk for recorded media such as DVDs. More particularly, thisinvention relates to an apparatus for providing an automated,freestanding dispensing and retrieval system for automated retaildistribution of recorded media, which is linked to a central servercomputer using the Internet.

BACKGROUND

Retail outlets are commonplace hubs for sale or rental of recordedmedia. These outlets typically have a substantial inventory of opticalmedia, and therefore require a building to house the inventory andprovide a location for commerce. In addition, staff is required for saleand/or rental of recorded media, processing of returned media andrestocking of returned or new media. These requirements result inconsiderable overhead to a person or company seeking to run a businessthat trades in recorded media—for example, wages and rent must be paidregularly.

Some wishing to cash in on the recorded media trade have sought toreduce the aforementioned overhead by offering a limited supply ofrecorded media at an existing establishment, such as a conveniencestore. However, as staff is still required for sales, rentals andrestocking, others have attempted to reduce overhead associated with thetrade of recorded media through electronic commerce (EC). In this typeof business model, a customer submits an order for recorded media viathe Internet. A central warehouse then ships the ordered media throughthe mail, or using a private courier. The cost of operating a retaillocation is avoided with this business model. However, Internet-baseddistribution systems often have significant liabilities.

One such liability is that a customer must wait for an order to beshipped from a warehouse location. Another disadvantage is that stockmay not be available at the time the order is processed. If stock isunavailable, an order may be placed on back-order until the requestedrecorded media is available, at which time the customer may no longer beinterested in the requested media. Alternately, the order may becanceled. Another significant disadvantage of an Internet-baseddistribution system is the impracticality for media rental. The rentalbusiness is one of immediacy; a customer will rent an item that isavailable immediately, but may not rent if it is not availableimmediately. A customer is much less likely to rent an item that isshipped after ordering, requiring days for delivery. In addition, once acustomer is finished with a rented item, that customer must deal withthe inconvenience of return-shipping the media to the distributionlocation.

SUMMARY

There is need for a system for automated dispensing and retrieval ofrecorded media that takes advantage of the benefits of Internet-baseddistribution (such as creation of customer accounts, electronic paymentand accrual of valuable customer information) while eliminating theaforementioned disadvantages (such as an extended waiting period to viewan ordered media after rental and the requirement for return-shippingthe media). There is also a need for a system for automated dispensingand retrieval of recorded media that eliminates the need for a retailoutlet, attendant staff and associated expenses.

In one embodiment, a system for an automated dispensing and retrievalkiosk for recorded media includes a plurality of vertical racks in acircular formation, each rack configured for storing a plurality ofrecorded media. A customer interface allows a customer to select orreturn a recorded media. A robotic element delivers the selectedrecorded media from the vertical racks to a media output, at thecustomer interface. The element also delivers a returned recorded mediafrom a media input at the customer interface to the vertical racks. Acomputer controls operation of the kiosk, and an Internet interfaceconnects the kiosk to the Internet.

In one embodiment, a system for an automated dispensing and retrievalkiosk for recorded media includes a kiosk body; a storage subsystemwithin the body, for storing a plurality of recorded media; apresentation device supported in association with the body forpresenting information to a customer; a customer interface forinteracting with the customer in a transaction for a recorded media; acomputer for controlling operation of the kiosk; and a telecommunicationsubsystem for remote administration and billing interface with thecomputer. Program logic configured for interaction with the presentationdevice, facilitates selection and presentation of a particular categoryfrom the recorded media to consumers, according to predeterminedselection criteria.

In one embodiment, an improvement in a kiosk used for dispensing andretrieval of recorded media includes a telecommunications system forexchanging data between a central administrator and the kiosk. The kioskhas electronic controls, responsive to instructions from the centraladministrator, for governing administration of the kiosk according to aselected one of a plurality of states. The include a first state whichprovides for automatic administration of the kiosk; and a second statewhich provides for remote administration of the kiosk via thetelecommunications system, according to the instructions from thecentral administrator. The first state is governed by programinstructions providing for one or more of: selecting a mix of recordedmedia for the kiosk inventory; converting a recorded media from rentableto saleable; performing software upgrades from one or more remotelocations; performing analysis of the kiosk; predicting maintenance ofthe kiosk; determining an alarm condition; generating an alarm inresponse to the alarm condition; and performing maintenance of the kiosk

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a perspective view showing a system for an automateddispensing and retrieval kiosk for recorded media, in accordance withone embodiment.

FIG. 1B is a perspective view of the kiosk of FIG. 1A, with atransparent front door.

FIG. 2 is a perspective view of the kiosk of FIG. 1B, with the frontdoor removed to show internal kiosk components.

FIG. 3 is a front perspective view of a horseshoe construct within thekiosk of FIG. 1, including a storage assembly for recorded media, arobotic element and an input/output module.

FIG. 4 is a rear perspective view of the horseshoe construct of FIG. 3.

FIG. 5A is a front perspective view of the horseshoe construct andstorage assembly of FIG. 3.

FIG. 5B is a front perspective view of the horseshoe construct androbotic element of FIG. 3

FIG. 5C is a front perspective view of the horseshoe construct andinput/output module of FIG. 3

FIG. 6A-6C are perspective views of the robotic element of FIG. 5B, witha gripping assembly for gripping and moving recorded media within akiosk.

FIG. 7A is a side perspective view of the gripping assembly of FIGS.6A-6C.

FIG. 7B is an alternate side perspective view of the gripping assemblyof FIG. 7A.

FIG. 8A is a front perspective view of the input/output module of FIG.3.

FIG. 8B is a rear perspective view of the input/output module of FIG.8A.

FIG. 9 is a front perspective view of a system for an automateddispensing and retrieval kiosk with two customer interfaces, inaccordance with one embodiment.

FIG. 10 is a front perspective view of the kiosk of FIG. 9, with a frontdoor removed to show internal kiosk components including a horseshoeconstruct

FIG. 11 is a front perspective view showing the horseshoe construct ofthe kiosk of FIG. 10 in further detail.

FIG. 12 is a schematic view of the kiosk of FIG. 1A, illustratingexemplary display wings and an exemplary modular display topper.

FIG. 13 is a block diagram illustrating exemplary functionality andmodularity of the kiosk of FIG. 1A.

FIG. 14 shows a top schematic view of a system for an automateddispensing and retrieval kiosk for recorded media, with floor mountedgraphics that demarcate an area proximate to the kiosk, in accordancewith one embodiment.

DETAILED DESCRIPTION

Systems and methods now disclosed illustrate networked, automated kiosksthat not only automatically perform physical dispensing and retrieval ofrecorded media, but that also collect data from transactions and otherevents and then report said data to a central database. This aggregationof information provides for remote tracking and analysis of data using avariety of metrics such as transaction time, transaction volume,customer information, inventory levels, etc. Reports of theaforementioned are for example generated according to the reportframework summarized in Appendix K, and in accordance with exemplarysoftware architecture outlined in Appendix L.

FIG. 1A shows a schematic perspective view of one embodiment of a systemfor an automated dispensing and retrieval kiosk for recorded media.System 100 includes a kiosk 101, having a kiosk body 102 that is forexample shaped as a half cylinder with a front panel or door 104. Acustomer interface assembly 106 is for example mounted with door 104 andincludes a customer interface 108, a card reader 110 for readinginformation from a card such as a credit or debit card, and aninput/output module 112. As shown, customer interface 108 may be aliquid crystal display (“LCD”) touch screen 108; however, customerinterface 108 may alternately be a combined display screen and keyboardand/or voice recognition device. Input/output module 112 includes amedia input 114 for receiving recorded media into kiosk 101, and a mediaoutput 116, for dispensing recorded media from kiosk 101. Media inputand output 114, 116 are for example slots which may include one-waydoors or other covers.

FIG. 1B shows a schematic perspective view of kiosk 101 with atransparent door 104, for illustration of internal kiosk components. Astorage subsystem such as horseshoe construct 118, has a plurality ofvertical racks 120 suitable for storing a plurality of recorded media,such as DVDs. Horseshoe construct 118 is illustratively shown as asemi-circle, but may also be formed as a complete circle, or any partthereof. As used herein, “circular formation” refers to any formationalong a complete circle, or any portion thereof. Racks 120 are arrangedin said circular formation, and their size and number is selectable, forexample according to the total number of media to be stored thereinand/or the shape of horseshoe construct 118. Arranging vertical racks120 in a circular formation may increase the packing density of recordedmedia within the kiosk

FIG. 2 shows a perspective view of system 100 with front door 104 ofkiosk 101 removed, to further illustrate kiosk internal components. Asshown, vertical racks 120 are for example mounted in a semi-circlewithin horseshoe construct 118 and are thereby proximate to a centralrobotic element 122. Recorded media storage capacity of kiosk 101 isbased upon a number and a vertical size of vertical racks 120.Specifically, the number and the size of vertical racks 120 may beselected based upon required storage capacity of kiosk 101. Use ofvertical racks 120 and horseshoe construct 118 may provide enhancedstorage of recorded media within kiosk 101, as compared to ‘carouseltype’ storage units, thereby increasing storage density of recordedmedia within kiosk 101.

As also shown in FIG. 2, kiosk 101 includes an internal computer 124 andpower supply unit 126. Computer (also referred to as computer module)124 includes at least a processing unit, volatile memory, storage unitand a telecommunication subsystem/communication interface for remoteadministration and billing interface with computer module 124. Computermodule 124 is for example a Windows XP based personal computerconfigured for operation within kiosk 101. Power supply unit 126 mayinclude an uninterruptible power supply (“UPS”) unit, for example havinga battery, to provide power to kiosk 101 in the event that an externalpower supply is interrupted. Power supply unit 126 may also includeother electronic components such as motion control electronics tooperate robotic element 122.

FIGS. 3, 4 and 5A-5C show perspective views of horseshoe construct 118.As shown in FIGS. 3 and 4, vertical racks 120 are for example spacedalong the curved portion of horseshoe construct 118, with roboticelement 122 positioned equidistant from the horseshoe ends; however,alternate numbers and positions of racks 120 and alternate positioningof robotic element 122 may be employed, as a matter of design choice.

FIGS. 5A-C emphasize particular elements of horseshoe construct 118. Forclarity, features of FIGS. 5A-C that are not specifically discussedherein below are depicted with dotted lines, with the emphasizedfeatures shown in solid lines. For example, as shown in FIG. 5A, eachrack 120 is arranged as a vertical tower including a plurality ofstacked shelves 128 for holding recorded media, and racks 120 partiallysurround robotic element 122. In one embodiment, each item of recordedmedia is enclosed in a media case configured for handling by roboticelement 112. The media case for example includes one or moregrip-enhancing features such as indentations or extrusions shaped tofit, respectively, corresponding extrusions or indentations of a y-axisgripping assembly 130 (FIG. 5B) of the robotic element 122.Grip-enhancing features may additionally or optionally include atextured area and/or a strip or patch of easy-grip material such assticky rubber, to facilitate gripping by gripping assembly 130.

FIG. 5B shows y-axis gripping assembly 130, which for example utilizesthe aforementioned specific case features to achieve secure gripping,and subsequent movement, of the recorded media within kiosk 101.Gripping assembly 130 is for example mounted with a rotational assembly132 of robotic element 122 (see also FIG. 6B) for rotating grippingassembly 130 into position with any of the surrounding racks 12. Roboticelement 122 for example facilitates movement of a gripped recorded mediaalong the x-, y- and z-axes, as illustrated in coordinate system 500. Inother words, as described further with respect to FIGS. 7A, 7B, grippingassembly 130 moves both horizontally and vertically (e.g., back andforth along the y-axis and up and down along the x-axis), in addition torotating at an angle θ with respect to the y-axis. Upon command bycomputer module 124, gripping assembly 130 for example rotates viarotational assembly 132 until proximate a shelf 128 associated with arequested media. As shown, input/output module 112 is positioned withinthe range of rotational movement of gripping assembly 130, for example,opposite robotic element 122 along horseshoe construct 118. Assembly130, driven by robotic element 122, may therefore retrieve the requestedmedia, pivot (via rotational assembly 132) into alignment with output116, and deliver the media through output 116. Conversely, upon commandand via rotational assembly 132, gripping assembly 130 for exampleretrieves a returned media from input 114, and delivers the returnedmedia to an associated shelf 128, for storage.

FIGS. 6A, 6B and 6C emphasize particular elements of robotic element122. In particular, FIG. 6A shows a y-axis drive motor 134, for movingy-axis gripping assembly 130 up and down along the y-axis, and arotational axis drive motor 136, for driving rotational assembly 132(shown in FIG. 6B). Gripping assembly 130 (FIG. 6C) for example rotates,via motor 136 and rotational assembly 132, to an angle θ with respect tothe x-axis, the angle θ corresponding with a particular rack 120. Motor134 moves gripping assembly 130 up or down, into position with a shelf128 associated with a requested media. Gripping assembly 130 retrievesthe media, rotates along the x-y plane via motor 136 and rotationalassembly 132, and raises or lowers along the y-axis via motor 134 intoposition with output 116, to deliver the requested media. Media output116 for example includes one or more sensors to verify removal of themedia case from output 116.

FIGS. 7A and 7B show perspective views of z-axis gripping assembly 130.Assembly 130 for example includes a media gripper 138, sequenced by agripper motor 140, such as a camshaft mechanism, to grip and release amedia case. In one example of operation, robotic element 122 selects amedia case (containing a recorded media) from a shelf 128 of a verticalrack 120. A grip sensor (not shown) for example indicates that the caseis securely held by gripper 138, prior to delivery of the recorded mediato output 116. In particular, once the case is securely held, a x-axisdrive motor 142 moves gripping assembly 130 backward and forward alongthe x-axis (or back and forth at an angle θ in the x-y plane). Back andforth motion of gripping assembly 130 is for example facilitated bylinear bearings 144 (FIG. 7B). Gripping assembly 130 may thus moveforward to retrieve a deposited case from input 114, grip the case usinggripper 138, and move backwards via x-axis drive motor 142, taking thecase with it. The case may then be delivered, through the aforementionedrotational, up and down, and back and forth movements, to an associatedshelf 128, for storage. As shown in FIGS. 7A and 7B, up and downmovement of gripping assembly 130 along the y-axis may be facilitated byy-axis bearings 146 and a y-axis leadscrew nut 148.

FIGS. 8A and 8B show respective front and back perspective views ofinput/output module 112 and illustrate input 114 and output 116 infurther detail. As shown, an input door solenoid 150 facilitates returnof media through input 114.

As previously noted, media cases used with the described automateddispensing and retrieval kiosk may include features for facilitatinggripping by gripping assembly 130. Such cases may also incorporateelements for indicating damage or abuse to recorded media within thecase. For example, the media case may include a damage indicator forindicating possible damage to the case and/or recorded media containedtherein. Kiosk 101, through use of the one or more case sensors 152located at input 114, for example reads a temperature indicator such asa temperature sensitive coating on a returned media case to determine ifthe media case (and thus the recorded media therein) has been subjectedto extremes of temperature, potentially damaging the recorded media.Case sensors 152 read for example detect a color or compositional changein the aforementioned temperature sensitive coating. Alternately oroptionally, case sensors 152 may be temperature sensors, to sense anactual temperature of the case. In one embodiment, if a case sensor 152determines damage to a media case, a case rejection mechanism incommunication with the sensor 152 (for example by internal circuitry),prevents return of the damaged case at media input 114. In one aspect, asubscriber service may be enforced by use of a subscriber case thatpresents a unique electronically scannable indicia to identify that thecase is authorized for use in subscription use or use within aparticular kiosk or sub-group of kiosks, etc. A user may present thiscase for scanning and authorization to proceed with a transaction. Thesubscriber may have pre-approved billing arrangements.

As also shown in FIGS. 8A and 8B, a kiosk sensor such as camera 154 isfor example mounted with kiosk 101, to monitor operation thereof. Astill or video camera 154 may image a person engaging with the kiosk,for example in a credit card transaction. FIGS. 8A, 8B show one possibleposition of camera 154 relative to input/output 112. As shown, camera154 is mounted within kiosk 101; however, it is to be understood thatcamera 154 may equally be mounted external to kiosk 101, for example toone side of, or above, touch screen 108. The following Table Bidentifies screen shots, viewable on touch screen 108, as provided inAppendix M:

TABLE B Version 2 Screen Shots action.jpg addmovie.jpg anime.jpgauthorizing.jpg authorizingWithTrivia.jpg cartwpromo.jpg checkout.jpgcomedy.jpg delivering.jpg DeliveringDVDBuy.jpg DeliveringDVDRent.jpgdeliveringsam.jpg DiscDoesnotBelong.jpg DoYouNeedMoreTime.gif Drama.jpgernail.jpg family.jpg foreign.jpg helphowdoi.jpg helpMaxDVD.jpghelpscreen.jpg helpscreenmore.jpg home.jpg horror.jpg identifying.jpgidentifyingwithTrivia.jpg InitializingScreen.jpg keyboardzip.jpgMachineFullForReturn.jpg Main.gif Main.jpg mainWithWhiteBackground.jpgMaxDiscExceeded.jpg more.jpg MovieDetail.jpg moviedetailgod.jpgmoviedetailpay.jpg moviedetailsam.jpg moviedetailscary.jpgmoviedetailtriplets.jpg newrelease.jpg newreleasemore.jpgOpsDiscNotCurrentlyAvailable.jpg OpsExpiredPaymentCard.jpgOpsPaymentCardNotRecognize.jpg OpsPromoNotRecognize.jpgOpsServerCommDifficulties.jpg OpsTitleUnavailable.jpgOpsUnableToProcessRental.jpg OpsUnableToReceive.jpgOpsUnableToVerifyZip.jpg OpsUnableVerifyPaymentCard.jpg payment.jpgpayment735.jpg paymentemail.jpg paymentemail735.jpg paymentpromo.jpgpromoscreen.jpg promowhatis.jpg PushDiscAllTheWay.jpg QuickPoll1.jpgQuickPoll2.jpg quickpolla.jpg Remove.jpg RentalAgreement.jpgrentscreen.jpg rentscreen1disc.jpg rentscreen2.jpg return.jpgreturn2.jpg ReturnDVD.jpg returnWithTrivia.jpg romance.jpg S1.jpg S2.jpgS3.jpg S4.jpg scifi.jpg selectmovie.jpg selectmovieadd.jpg sports.jpgStartupError.jpg thankyou.jpg thankyou735.jpg thankyoupromo.jpgthankyoureturn.jpg thankyoureturnWithTrivia.jpg thankyouWithTrivia.jpgTool_BadSlots.jpg Tool_BarCamPegTest.jpg Tool_CardReaderHID.jpgTool_Controller.jpg Tool_CycleTest.jpg Tool_InventoryCheck.jpgTool_Login.jpg Tool_Operator.jpg Tool_ServoParams.jpg toppicks.jpgUnableToAcceptCreditCard.jpg UnableToAcceptReturn.jpgUnableToRecognize.jpg viewall.jpg war.jpg bytes Version 2.5 Screen ShotsBuyConfirmationScreen.jpg CartScreen1.jpg CartScreen2.jpgEmailScreen.jpg MainScreen.jpg MainScreenTrailer.jpgMovieDetailScreen1.jpg MovieDetailScreen2.jpg MovieSelectionScreen.jpgPromoCodeDescriptionScreen.jpg PromoCodeScreen.jpgRentalAgreementScreen.jpg RentalSalesAgreementScreen.jpg ReturnDVD.jpgReturnThankYouScreen.jpg TakeDVD.jpg Tool_RemoveDiscs.jpgTransactionTimeOut.jpg UnableToRecognizeDVD.jpg ZipCodeScreen.jpg

FIG. 9 shows one exemplary system 200 with a kiosk 201 having twocustomer interfaces 202A and 202B. Customer interfaces 202A, 202B mayeach be similar to customer interface assembly 106 of FIG. 1A; eachincluding respective customer inputs (e.g., LCD touch screens) 204A,204B and input/output modules 206A, 206B, each input/output moduleincluding a respective input 208A, 208B for receiving recorded media,and an output 210A, 210B, for dispensing recorded media. Card readers212A, 212B for example read information from credit cards insertedtherein. Kiosk 201 may incorporate additional interfaces 202, as amatter of design preference. Likewise, two half-cylindrical kiosks 101or 201 may be positioned back-to-back to provide a cylindrical kioskstation, for example with multiple interfaces 202 positioned about thecircumference of the station.

FIG. 10 shows one view of kiosk 201 with a front door 214 removed forpurposes of illustration. Kiosk 201 includes internal horseshoeconstruct 216, with a plurality of vertical racks 218 and a roboticelement 220 having a y-axis gripping assembly (see FIG. 11). Powersupply 222 for example includes a UPS unit for powering kiosk 201 if anexternal power supply is interrupted. Other electronics, e.g., motioncontrol electronics for operating robotic element 122, may be furtherincluded with power supply 222. A computer module 224 for examplecontrols operation of kiosk 201.

FIG. 11 shows horseshoe construct 216, vertical racks 218, roboticelement 220 and y-axis gripping assembly 226 in further detail.Horseshoe construct 216, vertical racks 218, robotic element 220 andy-axis gripping assembly 226 are for example similar to horseshoeconstruct 118, vertical racks 120, robotic element 122 and y-axisgripping assembly 130 of FIG. 3. FIGS. 9, 10 and 11 are best viewedtogether with the following description.

In kiosk 201, robotic element 220 may deliver selected recorded media toone of input/output modules 206(A) or 206(B). For example, if a firstcustomer interacts with customer interface 202(A) and a second customerinteracts with customer interface 202(B), robotic element 220, usingy-axis gripping assembly 226, delivers a first recorded media, selectedby the first customer, to input/output module 206(A) and delivers asecond recorded media, selected by the second customer, to input/outputmodule 206(B). Input/output modules 206 may include one or more sensors(e.g., monitor sensors 358, FIG. 13) to determine acceptance of theselected recorded media by customers. Kiosk 201 may contain part or allfunctionality of kiosk 101, described above.

Systems 100, 200 may include a plurality of kiosks (e.g., one or more ofkiosk 101 and/or kiosk 201) co-located and ‘grouped’ together via akiosk-to-kiosk telecommunications device such as an Internet interface,or a telecommunications device facilitating interface between a centralserver and the kiosks. For example, kiosks 101, 201 regularlycommunicate operating conditions such as functional status, program oroperational errors, temperature and other environmental conditions, andCPU and memory load to a central administrator associated with thecentral server, according to update protocol governed by programinstructions included in hardware or software operable with computer124. Kiosks may likewise communicate with each other and the centralserver to provide additional inventory capacity at a particularlocation. For example, multiple kiosks may be provided at a locationwhere inventory of a single kiosk is frequently exhausted, to increaseinventory. These grouped kiosks may communicate (e.g., using theInternet, a wireless interface or a wired interface) inventory statusinformation directly with one another, enabling recorded media to belocated within any kiosk of the group. In another example, each of thegrouped kiosks communicates its inventory status to a server (e.g., aserver located on the Internet or with central administrator), which maythen be interrogated by one or more kiosks to locate stock of recordedmedia within other kiosks of the group. Program instructions for exampleprovide for listing of access to inventory information within andbetween kiosks, as exemplified in the Data Caching and Frameworkinformation of Appendix A.

In one example of operation, a potential customer requests a certainrecorded media from a first kiosk of a group. Where stock of therecorded media has been exhausted from the first kiosk, the first kioskcommunicates with other kiosks of the group (e.g., directly or via aserver) to locate stock of the recorded media. If the recorded media isstocked by one or more other kiosks of the group, the first kioskidentifies the one or more other kiosks, for example directing thepotential customer to the one or more other kiosks via a messagedisplayed upon a touch screen 108, 204A or 204B.

In one embodiment, where a first kiosk is exhausted of a recorded mediarequested by a customer, the first kiosk may locate and reserve stock ofthe recorded media within another kiosk of the group. If this reservedrecorded media is not claimed within a certain time period, thereservation may be automatically cancelled.

As shown in FIG. 12, a system for an automated dispensing and retrievalkiosk includes one or more presentation devices that for example serveas marketing display units. FIG. 12 depicts system 100 with kiosk 101including exemplary display wings 228 and an exemplary display topper230. As illustrated, display wings 228 and topper 230 are modularpresentation devices supported in association with kiosk body 102;however, it will be understood that display wings 228 and/or topper 230may also be integrated with kiosk 101, as a matter of design preference.Modular display wing 228(A) is illustratively shown with a plurality ofactive display panels 232 (e.g., LCDs) that may, for example, displayactive advertisements (e.g., film trailers) of remaining inventorywithin kiosk 101, or other information, through control of kiosk 101 (orvia the central server connected to kiosk 101). Modular display wing228(B) is illustratively shown displaying a static advertisement 234 ofrecorded media within kiosk 101; static advertisement may also displayother notices or advertisement information. As shown, modular displaytopper 230 has a single active display screen 236 (e.g., a cathode raytube display, a liquid crystal display, a back-lit four color display,etc.) and may include other audio visual equipment, such as lights andspeakers. Modular display topper 230 for example displays marketingmaterial (e.g., related to remaining inventory) or other informationupon screen 236.

FIG. 13 is a block diagram illustrating functionality and modularity ofsystem 100. FIGS. 1A, 1B, 2, 12 and 13 are best viewed together whilereading the following description. Computer module 124 is preferablyconnected to the Internet via an Internet interface 402, so that kiosk101 may initiate and verify credit card transactions. In one example,kiosk 101 makes a credit transaction via the Internet and then sends atransaction receipt to a customer's email account (thereby avoiding theneed to print paper receipts). Should an Internet transaction such aselectronic billing fail, an error message similar to those shown inAppendix C may be generated at the customer interface 108. A kioskcommunication framework is for example employed in governing e-commercein accordance with Appendix J.

Kiosk 101 may also include a local wireless interface 406 (e.g., a WiFiHub) that allows kiosk 101 to serve multiple business functions andprovide wireless connectivity to the Internet via Internet interface402.

Telecommunications device/internet interface 402 also allowsfunctionality of kiosk 101 to be managed or administered from a centraladministrator remote from the kiosk by a management team 504 or amaintenance team 502, for example employing operations summarized inAppendix D. Maintenance team 502 and management team 504 may beco-located or separate from one another. In an embodiment, calibrationsoftware 304 and monitor sensors 358 are accessible from remotemaintenance locations by maintenance team 502. In one example ofoperation, calibration software 304 may be automatically triggered bycomputer module 124 to perform routine checks on one or more components(e.g., robotic element 122, computer module 124, etc.) of kiosk 101.Calibration for example follows steps outlined in the Calibration ToolUser Manual, attached as Appendix G.

Results from these calibrations may then be available via Internetinterface 402, and/or automatically uploaded to maintenance team 502.Maintenance team 502, therefore, only need visit kiosk 101 when physicalmaintenance or repair is necessary.

Kiosk 101 may include one or more embedded controllers (e.g., embeddedcontroller 370) that have built-in processing capability and associatedfirmware (e.g., firmware 372). In one example, embedded controller 370may reside within robotic element 122 to initiate, control and completepredetermined mechanical operations based upon firmware 372.

In one embodiment, firmware 372 includes program instructions forinitiating, controlling and completing mechanical administration ofkiosk 101. Embedded controller 370 uses firmware 372 to identify and/orresolve software and/or mechanical problems that may occur within kiosk101, for example controlling mechanical kiosk components to performpredetermined mechanical functions. If a mechanical problem is detectedwithin kiosk 101, embedded controller 370 may restart one or moreembedded controllers, including itself, to attempt to resolve theproblem. In another example, if embedded controller 370 controlsmovement of one or more mechanical elements (e.g., elements withinrobotic element 114), firmware 372 may also include instructions thatmove these mechanical elements through one or more sequences designed torepair certain mechanical problems. For example, firmware 372 includesinstructions that move the mechanical elements to dislodge interferingobjects and/or reposition moveable items. Where recorded media becomesdislodged or out of position, firmware 372 may include instruction toreturn the recorded media to appropriate inventory position withinvertical racks 120.

Embedded controller 370 may further employ firmware instructions todetect and/or diagnose potential error conditions within kiosk 101,using one or more monitor sensors. A plurality of monitor sensors 358(e.g., cameras, lasers, “stack sensors”, contacts, etc.) may be mountedinternally and/or externally to kiosk 101 to monitor operation thereof.Controllers 370 for example acquire data from monitor sensors 358 andprocess the data with algorithms of firmware 372 to determine whether analarm state exists. Firmware 372 may further provide functionality toreport acquired and/or processed data indicative of an alarm state toother embedded controllers and/or to computer module 124.

In one embodiment, diagnostic software 319 within computer module 124acquires information from monitor sensors 358, and reports thisinformation, as a status of kiosk 101 for example, to management team504 and/or maintenance team 502 via Internet interface 402. Diagnosticsoftware 319 may also process this information to determine if an ‘alarmstate’ has occurred. Kiosk monitoring for example provides sensors 358and basic alert support as described in the attached Appendix I.

To increase alignment tolerances of mechanical components duringconstruction of kiosk 101, computer module 124 and embedded controllers(e.g., embedded controller 370) may include calibration software 304(where included with embedded controllers 370, calibration functionsdescribed herein may be stored as firmware 372). A calibration processof calibration software 304 may, for example, determine alignment ofrobotic element 122 with vertical stacks 120 of horseshoe construct 118after kiosk 101 is constructed. In particular, embedded controllerswithin robotic element 122 may interface with one or more roboticsensors 358 to provide location feedback to calibration software 304.Calibration software 304 may, for example, populate a database/table 322with location/position and tolerance information determined during thecalibration process. Once the calibration process is complete,database/table 322 may be utilized during operation of kiosk 101.Further calibration may occur periodically, and/or upon command frommanagement team 204 and/or maintenance team 502. In one example,database/table 322 is updated with calibration information during normaloperation of kiosk 101. Calibration information is for example generatedat pre-programmed intervals, or in response to external triggers.

System 100 may also include one or more proximity sensors 354 to detectproximity of persons to kiosk 101. For example, proximity sensor 354mounted on the front of kiosk 101 may detect a person (i.e., a potentialcustomer) approaching kiosk 101. Metric software 314 within computermodule 130 may collect proximity information from proximity sensor 354to build statistical information of a person's behavior around kiosk101, for example. This statistical information may include one or moreof: a time of detection, a length of detection (i.e., how long theperson stayed proximate to kiosk 101), distance of the person from kiosk101, etc. Other statistics may be derived from this information; forexample, computer module 130 may also determine ratios between personsproximate to kiosk 101, persons interacting with consumer interface 104of kiosk 101 and customers completing a transaction with kiosk 101,thereby determining a number of persons passing but not interactingand/or transacting with kiosk 101.

System 100 may also include biometric sensors 356 to identify personsinteracting with customer interface 104. In one example, biometricsensors 356 may allow kiosk 101 to determine a person's approximate ageby analyzing their facial images. In another example, biometric sensors356 may allow kiosk 101 to identify individual people utilizing one ormore of: facial image recognition, fingerprint recognition, irisrecognition, etc.

Kiosk 101 may also include one or more interfaces to allow media to bedownloaded into alternative media storage devices. Kiosk 101 may, forexample, include hardware to distribute recorded media to an alternatestorage device (e.g., by recording data from the recorded media to analternate format). In another example, kiosk 101 may include a localwired interface 404 (e.g., an Ethernet port or a USB port) to allow anexternal media storage device to connect to kiosk 101 and receivetransmitted media. In another example, kiosk 101 includes a localwireless interface (e.g., Bluetooth, 2.4 GHz wireless 802.11 network,infra-red, optical, etc.) that allows a data storage device, proximateto kiosk 101, to receive transmitted media. In one example, recordedmusic is transmitted to an MP3 player.

Kiosk 101 may also include hardware to allow recorded media to bedelivered to hardware distant from kiosk 101. For example, recordedmedia may be purchased at kiosk 101 and delivered (e.g., via email) toone or more remote destinations. Computer module 124 may thereforeinclude appropriate software to control and allow transfer of recordedmedia to one or more other formats, and may also include software toauthorize and/or distribute media from a remote location to anotherremote device.

FIG. 14 shows a system 1400 for an automated dispensing and retrievalkiosk, e.g., kiosk 101, with floor mounted graphics 600 that demarcatean area 602 proximate to kiosk 101. These floor mounted graphics 600 mayinclude active elements 604 for interaction with persons proximate tokiosk 101. For example, active elements 6064 may generate one or moresensory experiences within area 602, such as lighting, odor, sound,humidity, etc.

Returning to FIG. 13, an active display wall 506 may be associated with,or attached to, kiosk 101 to provide additional advertisement display.For example, active display or video wall 506 may represent modulardisplay wing 228(A), FIG. 12, and thus include one or more activedisplay units such as LCDs that display information relating to currentinventory of kiosk 101 (e.g., to display trailers for films of inventorywithin kiosk 101). For example, hardware or software of computer 124(and/or a remote server 508 in communication with kiosk 101 viatelecommunications device/Internet interface 402) includes algorithmsfor determining the available inventory and advertising one or morerecorded media of the available inventory on the display units or oncustomer interface 108.

Video wall 506 for example receives instructions based upon the recordedmedia therein, such as instructions to display trailers of new orunder-rented media. In another example, active display wall 506 is notnecessarily proximate to kiosk 101, but is still controlled by kiosk 101(e.g., via an Internet or wireless connection).

Kiosk 101 may further include one or more integrated internalenvironmental control units 360 that allow operation of kiosk 101 withinextreme environments. Environmental control units 360 maintain acontrolled environment within kiosk 101, for example. If kiosk 101 isutilized in a controlled indoor environment, environmental control units360 may be superfluous. However, if kiosk 101 is located in an outdoorenvironment, environmental control units 360 may include one or moremodular units such as a heater unit 362, a cooler unit 364 and ahumidity unit 366.

Computer module 124 may contain inventory management software 320 formanaging inventory of recorded media within kiosk 101, as exemplified inthe data and caching framework provided with Appendix A. In one example,inventory management software 320 performs calculations to determine oneor more inventory alarm conditions. For example, inventory managementsoftware 320 may determine an alarm condition when inventory drops belowa certain number. In another example, inventory management software 320may determine an alarm condition when inventory exceeds a certain level(i.e., when inventory overstocking is in operation). When an alarmcondition occurs, an alarm is generated and may be provided to one ormore of cell phones, pagers, email addresses, etc., via Internetinterface 402. Inventory management software 320 may also includeinventory overstocking routines 324, thereby maximizing operation ofkiosk 101, for example. Alarms related to inventory, kiosk operationalstatus and other kiosk parameters may be generated and broadcastaccording to a system monitor service that is for example independent ofkiosk system 100 software, in accordance with the architectural overviewprovided in Appendix F.

Inventory management software 320 may also include media selectionroutines 326 utilizing algorithms to select a recorded media mix forstocking kiosk 101, based upon historical performance of specificrecorded media. Media selection routines 326 may analyze historicalinformation relating to consumer selection of a specific recorded mediato predict future selection levels.

Computer module 130 may also include shopping cart software 308 thatimplements a shopping cart feature for use by customers interacting withcustomer interface assembly 106. In one example, the shopping cardfeature operates as a transaction selection aggregation tool.

Computer module 130 may also implement suggestive selling routines 328(shown within inventory management software 320 for purposes ofillustration) that implement a ‘rent-me’ feature that allows a shortcutto certain recorded media, for example from an initial screen display ora main menu of the customer interface. The ‘rent-me’ feature may furtherimplement a most direct path to transaction completion for the recordedmedia. In one example, a customer presses one button to initiate atransaction. The customer may select a title or icon on an initialscreen of customer interface 108 to progresses immediately to a paymentstage requesting a credit card to be presented.

Suggestive selling routines 328 within inventory management software 320may, for example, make certain recorded media (e.g., new and/or populartitles) directly available from an initial interaction screen ofcustomer interface 104. Screens other than the initial screen ofcustomer interface 108 may also include buttons that directly initiatetransactions. Additionally, system 100 may include program logic forselecting and presenting a particular category from the recorded mediato consumers according to predetermined selection criteria, includingstatistical information such as historical consumer preference of media,available inventory, excess inventory and inventory for sale. Theparticular category, and/or advertising associated therewith, is forexample presented to the consumer on display wings 228, topper 230 orcustomer interface 108. The statistical information may likewisefacilitate determination of media to offer with the rent-me feature.

Computer module 124 may also include remote upgrade software 310,whereby a remote station (e.g., management team 504 and/or maintenanceteam 502) may send new software to computer module 124. Upgrade software310 facilitates download, install and execution of the new softwarewithout local interaction (i.e., without requiring personnel to attendkiosk 101). In one example, upgrade software 310 allows computer module124 to periodically (e.g., daily or weekly) interrogate a remote server508 (e.g., accessible by maintenance team 502) to download new software,if available. Thus, computer module 124 is automatically updated withoutexternal initiation. Upgrades may be automatically verified, for exampleby implementing the testing plan outlined in Appendix E.

Computer module 124 may also include maintenance software 312 thatallows maintenance of kiosk 101 to be performed from a remote location.For example, maintenance team 502 may interrogate maintenance software312 to determine one or more internal temperatures and other internalenvironmental parameters of kiosk 101. Kiosk 101 may, for example,include one or more internal environmental sensors 352 that interface tomaintenance software 312. Maintenance software 312 may also determinewhen critical maintenance of kiosk 101 is necessary, and mayautomatically request this maintenance of maintenance team 502, and/orperform critical maintenance, where possible. In another example,algorithms within maintenance software 312 may predict and requestpreventative maintenance, thereby preventing failure of kiosk 101. Suchmaintenance is not limited to physical maintenance of mechanisms withinkiosk 101, but may also include maintenance of data and software ofkiosk 101.

Computer module 124 may also include metric software 314 that monitorstransactions of recorded media to determine certain metrics and mayexport these metrics to other servers. Metric software 314 may, forexample, deliver point of sale demographic data, derived from thesemetrics, to other servers that may monitor more than one kiosk, Inanother example, metric software 314 delivers demographic data to ratingservers.

Computer module 124 may also include survey software 316 invoked to runa survey acquisition funded from external sources (i.e., a survey paidfor by an external entity). In one example, a survey may specificallytarget customers that complete transactions for one or more specificrecorded media. Upon request for or completion of a transaction for apredetermined recorded media, computer 124 may run software 316 topresent a survey at customer interface 108, for example posing a seriesof consumer queries chosen from the poll questions presented in AppendixB, to gain metric data. The gained data may be used to update thestatistical information utilized in connection with the rent-me andadvertising capabilities described herein.

Inventory management software 320 may also include a suggestive sellingalgorithm 328 that actively promotes marketing of remaining inventoryitems, thereby improving inventory turnover of kiosk 101. In oneexample, suggestive selling algorithm 328 may modify one or moremarketing displays of kiosk 101 to advertise remaining inventory items.

If a customer inputs an email address in order to receive a transactionreceipt, this email address may be stored within kiosk 101 and/or sentto remote server 508 that is for example accessible by management team504, for marketing purposes. Further, a customer may be given anopportunity to input a second email address (e.g., an email address of afriend) to receive invitations based upon the customer's transaction. Inone example, a customer may input one or more friends' email addressesto receive advertisements for a certain recorded media; these emailaddresses may also be stored and used for marketing purposes. In oneexample, emails containing advertisements, which may be selectedaccording to the aforementioned statistical information, may beperiodically generated and sent by kiosk 101. In another example, kiosk101 may allow a person interacting with customer interface 108 to sendan advertisement to an email address. For example, if a person,interacting with consumer interface 108, touches an advertisement on thescreen, kiosk 101 may request an email address from the person and thensend a copy of the advertisement to the email address. This emailaddress may also be stored for marketing purposes. Further, kiosk 101may include promotional codes within these emails that allow therecipient to receive one or more transactional discounts.

Kiosk 101 may also be utilized for public service announcements.Computer module 124 may include alert software 318 that allows kiosk 101to periodically connect to one or more government agency databases(e.g., via the Internet) to download one or more public serviceannouncements or alerts. For example, kiosk 101, utilizing alertsoftware 318 and Internet interface 402, may automatically, or uponcommand from a remote server such as server 508, connect to a governmentserver and download one or more amber alerts and/or terror alerts. Thesealerts may then be displayed on one or more advertisement/marketingdisplays (e.g., modular display topper 230, display wings 228A, 228Band/or customer interface 108) of kiosk 101. In another example ofoperation, these alerts may be sent to kiosk 101 manually (e.g., viamanagement team 504) for display on one or more marketing displays ofkiosk 101.

Where kiosk 101 operates for recorded media rental (i.e., allowing acustomer to rent one or more recorded media from an inventory ofrecorded media stored within kiosk 101), inventory management software320 may provide for converting a recorded media item from rentable tosaleable. For example, one or more software algorithms monitor rentalfrequency of recorded media and thereby make decisions, based onpredetermined limits, thresholds and other information, to convert oneor more inventory items from rental items to sale items. For example, ifkiosk 101 has twenty recorded media of one film, as this film becomesless popular the frequency of rental of associated recorded mediareduces. Algorithms of inventory management software 320 may thendetermine that ten of the twenty recorded media containing this film maybe sold, for example. As the frequency of rental for the remaining tenrecorded media reduces further, algorithms of inventory managementsoftware 320 may determine that stock of associated recorded mediashould be reduced further. As items of inventory are sold, kiosk 101 mayinform management team 504 that space is available within kiosk 101 fornew recorded media, for example.

The exemplary source code of Appendix C, in compiled form, may be usedto provide program instructions configuring system 100/200 foroperations as described herein, where the program instructions mayreside on circuitry, for example as shown in the case of computer 124and embedded controller 370 (for purposes of illustration, Appendix Cmay be viewed with Appendix H, which provides exemplary case studies ofcode migration). Unless otherwise noted, it will be appreciated thatwhat is shown is a non-limiting embodiment and the circuitry may be morebroadly provided on any electronically programmable system, such as acomputer having a single processor, multiple processors or in adistributed processing environment. Likewise, data storage may be localto the kiosk, adjunct to a server, or in a distributed or shareddatabasing environment.

Changes may be made in the above systems without departing from thescope hereof. As apparent from reading and fully understanding thisspecification, kiosks 101, 201 are modular in both functionality andserviceability. These modules may include software and hardware. Inparticular, these modules are field selectable, replaceable andmaintainable, for example facilitating configuration of kiosks 101, 201to provide functionality as desired for various levels of business andmaintenance. It should thus be noted that the matter contained in theabove description or shown in the accompanying drawings should beinterpreted as illustrative and not in a limiting sense. The followingclaims are intended to cover all generic and specific features describedherein, as well as all statements of the scope of the present method andsystem, which, as a matter of language, might be said to falltherebetween.

We claim:
 1. A kiosk for an automatically dispensing and receivingrecorded media, the kiosk comprising: a plurality of circular stackedshelves, each shelf configured for storing a plurality of recordedmedia; at least one customer interface for interacting with a customerto allow selection, delivery and return of one or more of the recordedmedia; a media output; a media input; a robotic element configured to(a) deliver selected recorded media from the stacked shelves to themedia output and (b) deliver returned recorded media from the mediainput to the stacked shelves; and a controller including processingcircuitry and memory, the memory having instructions that, when executedby the processing circuitry, cause the controller to control operationof the robotic element, wherein the controller is further configured toreceive maintenance instructions from a remote central administratorthat, when executed by the processing circuitry, cause the controller totest the performance of the robotic element.
 2. The kiosk of claim 1wherein the robotic element further comprises a gripping assemblyconfigured to grasp a case containing the recorded media.
 3. The kioskof claim 1 wherein the robotic element further comprises a grippingassembly configured to grasp a case containing the recorded media, thegripping assembly including a sensor configured to sense secure grasp ofthe case prior to movement of the case by the robotic element.
 4. Thekiosk of claim 1 wherein the robotic element further comprises agripping assembly configured to grasp a case containing the recordedmedia, and wherein the gripping assembly is configured to movevertically within the kiosk.
 5. The kiosk of claim 1 wherein the roboticelement further comprises: a gripping assembly configured to grasp acase containing the recorded media, and a y-axis motor coupled to thegripping assembly, wherein the y-axis motor is configured to raise andlower the gripping assembly relative to the stacked shelves.
 6. Thekiosk of claim 1 wherein at least a portion of the gripping assembly isconfigured to move horizontally with respect to the stacked shelves. 7.The kiosk of claim 1 wherein the robotic element further comprises: agripping assembly configured to grasp a case containing the recordedmedia, and an x-axis motor coupled to the gripping assembly, wherein thex-axis motor is configured to move the gripping assembly backward andforward relative to the stacked shelves.
 8. The kiosk of claim 1 whereinthe robotic element further comprises: a gripping assembly configured tograsp a case containing the recorded media; an x-axis motor coupled tothe gripping assembly, wherein the x-axis motor is configured to movethe gripping assembly backward and forward between a shelf containing aselected recorded media and the media input and output; and a y-axismotor coupled to the gripping assembly, wherein the y-axis motor isconfigured to raise and lower the gripping assembly relative to thestacked shelves to align the gripping assembly with the stacked shelfcontaining a selected recorded media.
 9. The kiosk of claim 1 whereinthe media input further comprises one or more case sensors configured toidentify a damage indicator on a case containing returned recordedmedia.
 10. The kiosk of claim 1 wherein the media input furthercomprises a case rejection mechanism configured to reject a damagedmedia case.
 11. The kiosk of claim 1 wherein the maintenanceinstructions cause the controller to move the robotic element through asequence for repairing a mechanical problem associated with the kiosk.12. The kiosk of claim 1 wherein the maintenance instructions cause thecontroller to move the robotic element to dislodge an object interferingwith operation of the robotic element.
 13. The kiosk of claim 1 whereinthe memory includes instructions that, when executed, cause thecontroller to move the robotic element to reposition an item associatedwith the kiosk.
 14. A kiosk for automatically dispensing and receivingrecorded media, the kiosk comprising: a plurality of circular, stackedshelves, each shelf configured to store a plurality of recorded media; acustomer interface configured to interact with a customer to allowselection, delivery and return of one or more of the recorded media; amedia input; a media output; a robotic element configured to (a) deliverselected recorded media from the stacked shelves to the media output and(b) deliver returned recorded media from the media input to the stackedshelves, wherein the robotic element includes a gripping assemblyconfigured to grasp a case containing the recorded media; and acontroller in communication with the robotic element, the controllerincluding processing circuitry and memory, the memory having firstinstructions that, when executed by the processing circuitry, cause thecontroller to move the gripping assembly horizontally and verticallyrelative to the stacked shelves, the memory further having secondinstructions that, when executed by the processing circuitry, cause thecontroller to test the performance of the robotic element.
 15. The kioskof claim 14 wherein the gripping assembly further includes a sensorconfigured to sense secure grasp of the case prior to movement of thecase by the robotic element.
 16. The kiosk of claim 14 wherein therobotic element further comprises a y-axis motor coupled to the grippingassembly and in communication with the controller, wherein the y-axismotor is configured to raise and lower the gripping assembly relative tothe stacked shelves.
 17. The kiosk of claim 14 wherein the roboticelement further comprises an x-axis motor coupled to the grippingassembly, wherein the x-axis motor is configured to move the grippingassembly backward and forward relative to the stacked shelves.
 18. Thekiosk of claim 14 wherein each stacked shelf includes a plurality ofstacked shelves configured to hold the recorded media, and wherein therobotic element further comprises: a gripping assembly configured tograsp a case containing the recorded media; an x-axis motor coupled tothe gripping assembly, wherein the x-axis motor is configured to movethe gripping assembly backward and forward between a shelf containing aselected recorded media and one of the media input or the media output;and a y-axis motor coupled to the gripping assembly, wherein the y-axismotor is configured to raise and lower the gripping assembly relative tothe stacked shelves to position the gripping assembly into alignmentwith a shelf containing a selected recorded media.
 19. The kiosk ofclaim 14 wherein the media input further comprises one or more casesensors configured to identify a damage indicator on a case containingreturned recorded media.
 20. The kiosk of claim 14 wherein the mediainput further comprises a case rejection mechanism configured to rejecta damaged media case.
 21. The kiosk of claim 14 wherein the grippingassembly includes a camshaft mechanism for gripping and releasing a casecontaining recorded media.